Social Media System and Methods for Parents

ABSTRACT

A system for managing a plurality of child profiles is provided that allows parents of children to capture a child&#39;s life events in media files, which are automatically imported into a life album for each child. The system also generates different views for the child&#39;s life album based upon both user-generated information and computer-generated information, and allows users to identify favorite media files for review using other tree structures. The system could automatically generate a face transformation video from life album media files, and could automatically generate expert queries from common issues gleaned from community discussions that are summarized and exported to experts for review.

This application is a continuation of U.S. application Ser. No.14/6747,143 filed Mar. 31, 2015. All extrinsic materials identifiedherein are incorporated by reference in their entirety.

FIELD OF THE INVENTION

The field of the invention is social media applications.

BACKGROUND

The background description includes information that may be useful inunderstanding the present invention. It is not an admission that any ofthe information provided herein is prior art or relevant to thepresently claimed invention, or that any publication specifically orimplicitly referenced is prior art.

All publications herein are incorporated by reference to the same extentas if each individual publication or patent application werespecifically and individually indicated to be incorporated by reference.Where a definition or use of a term in an incorporated reference isinconsistent or contrary to the definition of that term provided herein,the definition of that term provided herein applies and the definitionof that term in the reference does not apply.

Many parents wish to document and monitor their child's life well and indetail. Such documentation is especially important before the age of 18,while the parent is still a guardian of the child. With the demands ofeveryday living, however, it becomes harder to document a childs growthefficiently. Fortunately, many parents now have smart devices that couldbe used to improve the way parents can document their children's lives.

US 2009/0113350 to Hibtho teaches an application that creates a visualsummary of a hierarchically structured set of digital objects forfacilitating efficient access to such objects through the selection ofrepresentative summary objects. Such visual summaries could be organizedby year, month, and event information. A user could then choose to viewa top level folder node to present a user with a representative visualsummary object per year, or delve down to find a media object of choice,such as a digital image file. Hibino's application, however, createssuch hierarchical structures automatically by computer-generated captureinformation such as a creation date, and fails to query users for bothuser-generated and computer-generated information to create suchhierarchical structures.

U.S. Pat. No. 8,793,324 to Sellames teaches a system that providessystems and methods for exchanged information in a social media to beorganized according to discussion topics. Comments comprise text, butcould include additional non-text data, such as a photo, video, ordocument. All comments in Schames, however, must comprise text with thenon-text data. Schames fails to provide ways that a user could providecomments to a discussion topic in a no text form.

U.S. Pat. No. 8,054,343 to Cheatle teaches a system that assists a userof a device having an image to assist a user of the device to capturesubsequent images for a sequence of images that have substantially thesame location and device orientation. This allows the system toconstruct a sequence of images that could be meshed into a video showingchanges of an object over time. Cheatle's system, however, fails toautomatically identify and construct a sequence of transformations ofthe object over time by scanning through a library of images.

Thus, there remains a need for a system and method that will allow auser to automatically document and record relevant changes in a child'slife.

SUMMARY OF THE INVENTION

The following description includes information that may be useful inunderstanding the present invention. It is not an admission that any ofthe information provided herein is prior art or relevant to thepresently claimed invention, or that any publication specifically orimplicitly referenced is prior art.

The inventive subject matter provides apparatus, systems, and methods inwhich a computer system manages a plurality of child profiles.

It should be noted that any language directed to a computer systemshould be read to include any suitable combination of computing devices,including servers, interfaces, systems, databases, agents, peers,engines, controllers, or other types of computing devices operatingindividually or collectively. One should appreciate the computingdevices comprise a processor configured to execute software instructionsstored on a tangible, non-transitory computer-readable storage medium(e.g., hard drive, solid state drive, RAM, flash, ROM, etc.). Thesoftware instructions preferably configure the computing device toprovide the roles, responsibilities, or other functionality as discussedbelow with respect to the disclosed apparatus. In especially preferredembodiments, the various servers, systems, databases, or interfacesexchange data using standardized protocols or algorithms, possibly basedon HTTP, HTIPS, AES, public-private key exchanges, web service APIs,known financial transaction protocols, or other electronic informationexchanging methods. Data exchanges preferably are conducted over apacket-switched network, the Internet, LAN, WAN, VPN, or other type ofpacket switched network.

The computer system has a non-transitory computer-readable medium withinstructions stored on the computer-readable medium, that when executedon a processor perform a series of processes to enable a user of thesystem to manage a child profile. Users generally interact with thecomputer system through a user interface, for example a computer screenwith a mouse and a keyboard, or a touchscreen of a mobile device, suchas a phone or a tablet device. Preferably, the user invokes anapplication on the mobile device to connect to the computer system andperform tasks to manage one or more child profiles.

In one embodiment, a system could define a life album to a childprofile. A user of the system could use a life album user interface toadd media files to a child profile. The user could upload, for example,one or more images of the child, one or more videos of the child, and/orone or more text descriptions of the child using the life album userinterface. The system would then associate the uploaded media file (orfiles) with the child profile. Each media file preferably has timestampmetadata associated with it, such as a date and time of when the filewas created or uploaded. In some embodiments, the timestamp metadatacould be defined by a user through the life album user interface. Eachmedia file associated with a child profile is preferably stored by thesystem on a portion of the memory. In the case of a life album, themedia files associated with the child's profile is generally referred toas the life album memory.

The computer system could also be configured to automatically organizethe media files in accordance with metadata associated with the mediafiles. Preferably, the system uses the timestamp metadata, and organizesthe media files in accordance to one or more time categories. Forexample, a media file could have a year time category, season timecategory, month time category, day time category, hour time category,minute time category, and/or any other type of time category that isused to categorize the media file. Media files could also be placed incategories by a user of the system. For example, the life album userinterface could be configured to ask a user for a category, such as anevent name for a portion of the media files saved in the life albummemory of the child profile.

Once one or more categories have been assigned to a set of media filesin the life album memory, the system could generate a life album treestructure for the media files as a function of the categories. Forexample, from the root of the tree, a first level could be the yearassigned to the media file, the second level could be the month assignedto the media file, a third level could be the name of an event assignedto the media file, and a fourth level could be the type of the mediafile (e.g. an image file or a video file). The automatically generatedtree preferably has at least three levels, and uses a combination ofautomatically generated categories (e.g. time categories, file typecategories) and user-defined categories (e.g. event name category, eventtype category) from which to build the tree. Each media file generallyrepresents a leaf on the tree, being a final destination for a userperusing a life album through a life album user interface.

The life album tree structure is generally provided to the user throughthe life album user interface. In some embodiments, the tree structureis provided as a navigable tree from root to leaf. In other embodiments,the tree structure is provided one level at a time, allowing a user tonavigate from one tree junction to another tree junction like a user ofa computer navigates through a directory tree from folder to folder. Auser navigates a path to one or more leaves of the tree (generally amedia file) by issuing a set of commands from the life album userinterface to find one or more media files. Each child profile generallyhas its own life album tree, and a user could navigate to differentleafs on different child profiles to view media files associated witheach child profile. When the user finds a media file, the user couldview the media file and can also associate additional content with themedia file,

For example, the system could profile an input comment field to lifealbum user interface that a user could use to create a comment for anyof the media files. The input comment field is preferably configured toreceive a comment in different forms. For example, a user might use thesame input comment field to add a video comment (such as a videorecorded by a camera on the device) an audio comment (such as an audiostream recorded by a microphone on the device) or a text comment such asa text stream recorded by a keyboard user interface on the device). Insome embodiments, a single comment might have several different forms(e.g. a single comment with a video stream, audio stream, and a box oftext). When the system receives a comment in any form, the systempreferably then associates the comment with the media tile, and displaysthat comment to a user who has navigated to the media file, allowing auser viewing the media file to see that one or more comments areassociated with the media file.

The life album user interface could also provide a user with a togglespecific to each media file, allowing the user to toggle whether or notthe media file is a favorite media file of the user. If the useractivates the toggle via a favorite toggle command, the system registersthat an account associated with the user has marked the media file as afavorite of the user. When a user wishes to view his/her own favoritemedia files, the user could then navigate to a favorites user interface.

The system preferably generates a favorites album tree structure as afunction of the media files that have their “favorite toggle” activated.The favorites tree structure preferably has at least two levels, whereeach media file is a leaf in the tree structure. In one embodiment, thetree structure could be configured to have identifiers of child profilesas nodes in the first level, and identifiers of the toggled media filesin the second level. The favorites album tree structure is simpler thanthe life album tree structure, simplifying the media files intocategories for each child profile. When a user navigates to a leaf ofthe tree structure, the user could then view any added comments thathave been associated with the media file. Finalized favorites album treestructures could be displayed in a favorites user interface in anyappropriate manner.

The system could also provide a modeling user interface that enables asuser to provide one or more media files saved in the life album memoryto a modeling agency for use in an advertisement, or sonic otherpurpose. The system provides a modeling user interface that allows auser to select a media file from the life album memory and send arequest to the system to transmit the first media file to a distalmodeling computer system.. The system then transmits the selected mediafile to the distal modeling computer system for review. The distalmodeling computer system generally has its own user interface thatauthorized modeling agencies use to review the sent media file, anddecide whether or not to license the media file for use. The modelingagency could then transmit as purchase order (generally for a license tothe media file) to the computer system that manages the life album Auser could then decide whether or not to accept the purchase orderthrough the modeling user interface and, if accepted, the system coulddebit an account as a function of the purchase order (typically througha credit/debit account identified in the purchase order), and transmit alicense to a modeling entity as a function of the purchase order (themodeling entity is typically also identified in the purchase order).

The system is also configured to transmit one or more media files to acompetition entity for review in one or more competitions. The systemprovides a competition user interface to a user that allows that user toselect one or more media files as an entry to a competition. Preferablythe system is set up such that only one media file saved in a childprofile life album can be selected at a time, for example by associatinga child profile unique identifier with a media file entry, andpreventing additional media files from being saved with the same uniqueidentifier. The system could then save the selected media file to acompetition database functionally coupled with the system, where thecompetition database has a plurality of competition media files,generally from other child profiles or even submitted from othersystems. The plurality of competition media files now include the sentmedia file.

The system could then provide the plurality of competition media filesto a plurality of other competition user interfaces as entrants to thecompetition, allowing each competition user interface to vote for one ormore of the media files. Preferably, the system is configured such thateach user of the system can only cast a single vote for the duration ofthe competition. A competition duration might be for a specified periodof time, or might last so long as the system is online. In someembodiments, a media file entry could be entered in a plurality ofcompetitions, such as a weekly competition, a monthly competition, and ayearly competition. For each competition, the system preferably receivesa plurality of votes and calculates a tally for each of the competitionmedia files. At the end of a competition, the system could then providean indicator of a winner of the competition to the competition userinterface. The winner indicator is generally calculated as a function ofthe tally of votes for the media files, in some embodiments, multipleindicators could be used for multiple winners, for example a first placewinner, second place winner, or a third place winner.

The system is preferably also configured to render a face transformationvideo of a child in a child profile. Since a life album of a childprofile generally contains photos from throughout the child's life thesystem could be configured to compile a video from the various photosthat show how a face of the child has matured over time. The systemgenerally presents a face transformation user interface to a user, andreceives a command from the user to generate the face transformationvideo. The system then generally selects two or more facial images fromthe media files as a function of their timestamp metadata.

Where a media file is an image, the system could be configured to selectthe image itself as the facial image, or could be configured toautomatically crop the image around a face. Where the media file is avideo media file, the system could be configured to separate the videomedia file into a plurality of images for review. Generally, each facialimage is selected from a different time period, for example a firstfacial image could be selected from the month of January while thesecond facial image could be selected from the month of February. Suchtime periods could be predefined by the system, or could be defined by auser through the face transformation user interface. The system could beconfigured to look at all images derived from media files within a timeperiod, derive a facial clarity value for each of the images, and thenselect an image as a function of its derived facial clarity value. Insome embodiments, the system could be configured to recognize featuresof a child profile face by identifying features of the child profileface in an image associated with the child profile (for example a mainchild profile photo selected by a user), and could filter out imagesthat fail to contain a subset of the features of the child profile faceby comparing the identified features against each of the availableimages, or against the media files directly.

Preferably, the system automatically selects an image with the highestfacial clarity value. In some embodiments, where a user wishes moredirect control over the process, the system could be configured to showa user all of the image files derived from media files within each timeperiod through the face transformation user interface, and the user thenpicks an image from each of the presented sets of image files.Preferably, the system will rank the facial images by facial clarityvalue, presenting the user with facial images with the highest facialclarity first, and with facial images with the lowest facial claritylast. In some embodiments, the system could select a subset of theimages having a derived facial clarity value above a predefinedthreshold facial clarity value, such as 60% clarity, 70% clarity, 80%clarity, or 90% clarity, and could provide that subset to a facetramfonuation user interface for selection by a user.

Once the system has selected a set of facial images to construct thevideo from, the system can derive a set of facial features for eachfacial image, and generates a face transformation video containing eachof the facial images that aligns the facial images with one another inthe video as a function of the facial features. For example, the systemcould align a centerline of each face with a centerline of the video, orcould align the images such that they all have overlapping noselocations, or could rotate the image so that all of the images have asame facial angle. The system could save the face transformation videoto a face transformation memory location and present the video to theface transformation user interface.

Users of the system frequently collaborate with one another to discussissues, such as issues with a child of a child profile. The system couldprovide a parental collaboration user interface that allows users tosend a comment generation request to the system to generate a commentthread. Users of the system (generally parents) could then send commentsto the comment thread, which are then saved in the comment thread. Acomment thread generally contains comments from different users ofdifferent child profiles. For example, a first user of a first childprofile could provide a comment to a comment thread, and a second userof a second child profile could provide a different comment to the samecomment thread. A comment could comprise any sort of media content, forexample text, audio, and/or video content. As used herein, video contentcomprises an audio component and a video component.

Once at least two comments have been saved to a comment thread, thesystem could be configured to automatically detect a common issuebetween the plurality of comments saved to the comment thread. Where acomment thread comprises a plurality of different types of mediacontent, the system generally converts all media content to text contentbefore automatically detecting a common issue between the plurality ofcomments. Where media content is text content, no conversion isnecessary. Where media content is audio content, the system could useknown speech recognition algorithms to convert audio content to textcontent. Where the media content is video content, the system could useblown speech recognition patterns to convert the audio component of thevideo content to text content. Once the media content has been convertedto text content, the comment thread has a set of text content from whichthe system could derive a common issue.

In some embodiments the system derives a common issue by detectingrecurring phrases from the plurality of comments. The system could beconfigured to only detect recurring phrases of a minimum length, such asthree words, four words, five words, eight words, or 10 words, and/orthe system could be configured to only detect recurring phrases fromunquoted sections of a comment. As used herein, a “quoted” section of acomment is a section of a comment that quotes a previously saved commentin the comment thread, while an “unquoted” section of a comment is asection of a comment that does not quote a previously saved comment inthe comment thread (i.e. the “original” section of the comment) Thesystem could also be configured to detect whether an unquoted phrase hastwo or more literal phrase equivalents. As used herein, a “literalphrase equivalent” of a phrase is another phrase that is considered tobe equivalent to a detected phrase. For example the phrase, “a childwith a broken leg” could be considered an equivalent to the phrases “aboy with a broken leg” and “a girl with a broken leg,” or the phrase “amentally challenged child” could be considered equivalent to the phrase“a mentally handicapped boy.” Such phrase equivalents would beconsidered by the system to he the same recurring phrase.

In some embodiments, the system could be configured to detect aplurality of common issues. For example, a comment thread might discussproblems with mentally handicapped children, problems with autisticchildren, and problems with children having ADHD. In such embodiments,the system might rank the many common issues into a ranked list sortedby the number of recurrences having the most common issues at the top ofthe list and the least common issues at the bottom of the list. In someembodiments, a user of the parental collaboration user interface mighthighlight a phrase and send a notification to the system informing thesystem that the highlighted phrase is a potential common issue. Thepotential common issue could then be automatically added as a firstinstance of a recurring phrase, and the system could then automaticallydetect how many instances that recurring phrase has been used in thecomment thread. In some embodiments, a user of the parentalcollaboration user interface might even identify literal phraseequivalents, allowing users to “teach” a system about new common issuesand new literal phrase equivalents.

The following discussion provides many example embodiments of theinventive subject matter. Although each embodiment represents a singlecombination of inventive elements, the inventive subject matter isconsidered to include all possible combinations of the disclosedelements. Thus if one embodiment comprises elements A, B, and C, and asecond embodiment comprises elements B and D, then the inventive subjectmatter is also considered to include other remaining combinations of A,B, C, or D, even if not explicitly disclosed.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a hardware schematic of a system of the current invention.

FIG. 2 is a software schematic of a system of the current invention.

FIG. 3 is software schematic showing component elements of a life albummodule.

FIG. 4 is a software schematic showing component elements of a favoritesmodule.

FIG. 5 is a software schematic showing component elements of a modelmodule.

FIG. 6 is a software schematic showing component elements of acompetition module

FIG. 7 is a software schematic showing component elements of a facetransformation module.

FIG. 8 is a software schematic showing component elements of a parentalcollaboration module.

DETAILED DESCRIPTION

As used in the description herein and throughout the claims that follow,the meaning of “a,” “an,” and “the” includes plural reference unless thecontext clearly dictates otherwise. Also, as used in the descriptionherein, the meaning of “in” includes “in” and “on” unless the contextclearly dictates otherwise.

As used herein, and unless the context dictates otherwise, the term“coupled to” is intended to include both direct coupling (in which twoelements that are coupled to each other contact each other) and indirectcoupling (in which at least one additional element is located betweenthe two elements). Therefore, the terms “coupled to” and “coupled with”are used synonymously. The term “functionally coupled to” refers tocomputer devices that are coupled with one another through a network ina manner such that electronic information is transmitted to and from thecomputer devices.

Unless the context dictates the contrary, all ranges set forth hereinshould be interpreted as being inclusive of their endpoints, andopen-ended ranges should be interpreted to include commerciallypractical values. Similarly, all lists of values should be considered asinclusive of intermediate values unless the context indicates thecontrary.

The recitation of ranges of values herein is merely intended to serve asa shorthand method of referring individually to each separate valuefalling within the range. Unless otherwise indicated herein, eachindividual value is incorporated into the specification as if it wereindividually recited herein. All methods described herein can beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g. “such as”) provided with respectto certain embodiments herein is intended merely to better illuminatethe invention and does not pose a limitation on the scope of theinvention otherwise claimed. No language in the specification should beconstrued as indicating any non-claimed element essential to thepractice of the invention.

Groupings of alternative elements or embodiments of the inventiondisclosed herein are riot to be construed as limitations. Each groupmember can be referred to and claimed individually or in any combinationwith other members of the group or other elements found herein. One ormore members of a group can be included in, or deleted from, a group forreasons of convenience and/or patentability. When any such inclusion ordeletion occurs, the specification is herein deemed to contain the groupas modified thus fulfilling the written description of all Markushgroups used in the appended claims.

Various objects, features, aspects and advantages of the inventivesubject matter will become more apparent from the following detaileddescription of preferred embodiments, along with the accompanyingdrawing figures in which like minerals represent like components.

One should appreciate that the disclosed techniques provide manyadvantageous technical effects including improving the speed at whichmedia files are organized in a tree structure by automatically creatingpart of a tree structure and seeking manual input the create the otherpart of the tree structure, providing comment fields for media filesthat could accept more than just text.

The inventive subject matter provides apparatus, systems, and methods inwhich a computer system manages a plurality of child profiles.

In FIG. 1, a system 100 has a plurality of user interface modules 112,114, 116 wirelessly connected to a network 120 through wirelessinterface 122. These user interface modules 112, 114, and 116communicate with child profile computer system 130 having storage 140,which also communicates with computer systems 152, 154, and 156. Userinterface modules 112, 114, and 116 are shown euphemistically hasportable phones with touch-screen interfaces, but could be any computersystem having a user interface without departing from the scope of thecurrent invention, such as tablet devices, desktop computers, and PDAs.While each of the user interface modules 112, 114, and 116 have a userinterface of a touch-screen, speaker, and microphone, user interfacemodules 112, 114, and/or 116 could have other user interfaces withoutdeparting from the scope of the current invention, such as keyboards,mice, trackballs, and controllers. While each of the user interfacemodules 112, 114, and 116 are shown as being wirelessly connected tonetwork 120 through a wireless connection to wireless antenna 122, theuser interface modules could be functionally coupled to network 120 inany wired or wireless manner sufficient to transmit contentelectronically between the user interface modules and child profilecomputer system 130.

Network 120 is shown euphemistically as a cloud that functions toconnect a plurality of computer systems with one another. Network 120could be an intranet network, and is preferably the Internet, allowingthe connected computer system devices to connect not only with oneanother, but with all other computer system devices having access to theInternet.

Child profile computer system 130 has a processor configured to executeinstructions saved on a computer-readable medium. While child profilecomputer system 130 is shown as a single computer, child profilecomputer system 130 could be distributed between a plurality of computersystems in a plurality of different locations, all functionallyconnected through wired and/or wireless connections, without departingfrom the scope of the current invention. In a preferred embodiment,child profile computer system 130 is embodied on a plurality of bladeservers distributed among a plurality of locations that act as redundantfail-safes in case one or more blades fail. Storage 140 is anon-transitory computer-readable medium accessible by child profilecomputer system 130, and acts as a storage unit for storing organizedinformation by child profile computer system 130. Like child profilecomputer system 130, storage 140 could be distributed among a pluralityof systems, and distributed among a plurality of locations, so as to actas redundant fail-safes in case one or more storage devices fail.

Distal computer system 152, 154, and 156 are other computer systems thatare functionally connected to child profile computer system 130. Childprofile computer system 130 communicates with such distal computersystems in order to accomplish cooperative tasks. For example, distalcomputer system 152 could be a distal modeling computer system thatchild profile computer system 130 could transmit a media file to. Distalcomputer system 154 could be a remote transaction server, such as a bankor a middleman such as Paypal®, that child profile computer system 130could communicate with in order to conduct a transaction. Distalcomputer system 156 could be a remote social media server, such asFacebook® or Instagram®, that child profile computer system 130 couldcommunicate with in order to send and receive media content, such asphotos and videos. Child profile computer system 130 could be configuredto communicate with other computer systems through network 120 withoutdeparting from the scope of the current invention. The functions ofchild profile computer system 130 are further elucidated by analyzingthe software modules instantiated when its processor executes softwareinstructions stored on its computer-readable medium.

In FIG. 2, a software schematic 200 shows various software modules ofchild profile computer system 130. Child profile computer system 130 hasan interface module 210 which communicates with other computer systemsvia network 120 through known means, such as through a TCP/IP networkconnection through the Internet. The various systems that interfacemodule 210 sends and receives electronic information to include, forexample, distal user interface computer systems, distal modelingcomputer systems, distal social media computer systems, distaltransaction computer systems, distal licensing computer systems, anddistal competition computer systems. Child profile computer system 130also has various modules, such as life album module 221, favoritesmodule 222, model module 223, competition module 224, facetransformation module 225, and collaboration module 226. Each of thesemodules communicates with other computer system through interface module210, and sends and receives information to storage interface 231.Storage interface 231 could comprise a local non-transitory storagemedium within computer system 130, or could comprise an interface withstorage 140, but is preferably a combination of both, holding short-terminformation temporarily in local memory and long-term information forextended periods of time in storage 140. Each module performs tasks onbehalf of users and administrators to manage a plurality of childprofiles.

In FIG. 3, a software schematic 300 for a life album module, such aslife album module 310, has a computer interface connection 310, astorage interface 330, and a media file metadata generator 320. Computerinterface connection 310 communicates with interface module 210 torequest media files from a distal user interface, such as a userinterface on distal computer system 152. For example, interfaceconnection 310 could provide a button to a life album user interfacethat allows a user to transmit a photograph taken from a camera on thedistal computer system, or a video taken from a camera and a speaker onthe distal computer system, to the child profile computer system, orcould allow a user of the distal computer system to select a locallysaved media file from a library of media files for transmission to thechild profile computer system. Such media files could comprise metadata,such as a time that the media file was taken, a location the media filewas taken, a format, a resolution, and an identifier of an entity whotook the media file. Media files include image files containinggraphical data, audio files containing audio data, and video filescontaining both graphical and audio data.

Such media files, such as media files 311 and media files 314, couldthen be received by interface connection 310 from the life album userinterface. Media files 311 and 314 could be analyzed by metadatagenerator 320 to derive computer-generated metadata 312 and 315,respectively, that could be used to organize media files 311 and 314. Asused herein, “computer generated metadata” comprises metadataautomatically generated by a module of the child profile computersystem, such as metadata generator 320, by analyzing properties offiles. Such computer-generated metadata could be, for example, a yearassociated with the media file, a month associated with the media file,a day associated with the media file, an hour associated with the mediafile, a location associated with the media file, a media file type,and/or a unique identifier associated with the media file. Interfaceconnection 310 could also be configured to request and/or receiveuser-generated metadata 313 for media file 311 and user-generatedmetadata 316 for media file 314. As used herein, “user generatedmetadata” comprises metadata generated by a human user and sent to thechild profile computer system through a user interface. Such usergenerated metadata could comprise, for example, a name of an event thatis associated with a plurality of media files to group them alltogether, a description of a media file, a link to an associated mediafile, and/or a link to an associated child profile.

In some embodiments, metadata generator 320 also analyzes the media fileto determine which life album, or albums, the media file should beimported into. For example, a facial recognition algorithm such as thosedisclosed in U.S. 2014/0096018 to Iannucci or US 2013/0027569 toPariilski, both of which are incorporated herein by reference—could beused to recognize a child in an image or video and automaticallyassociate that media file with a particular life album. In someembodiments, the life album user interface could prompt a user if theuser wishes to import the media file into a plurality of child profilelife albums, such as when a plurality of blown children are found in thesame image. For such a facial recognition system to recognize a child, auser preferably selects one or more uploaded images as an “identifyingimage” for a child's life album. Since the facial features of a childtend to change dramatically within the first few years of a child'slife, the system preferably prompts a parent to upload an identifyingphoto more frequently during the first few months of a child's life thanduring later years of a child's life. For example, where a child is lessthan a year old, the system preferably prompts a parent to provide anidentifying image for the child once per month. However, where a childis between the ages of two and five, the system preferably prompts aparent to provide an identifying image once every 6 months, and where achild is between the ages of five and twelve, the system preferablyprompts a parent to provide an identifying image once every year.

Media file manager 330 saves media files 311 and 314 having associatedcomputer-generated metadata 312 and 315, respectively, and associateduser-generated metadata 313 and 316, respectively, into acomputer-readable storage medium for future access, such as storage 140.Media file, manager 330 could also organize the media files into variousviews to present to a user interface via interface connection 310. Forexample media file manager 332 could organize the media files into atree structure such as tree structure 332, which is generated as afunction of both computer-generated metadata and user-generatedmetadata. Generally, the upper levels of the tree structure closest tothe root are organized using computer-generated metadata and the lowerlevels of the tree structure closest to the leaves are organized usinguser-generated metadata. For example, the first level might organizemedia files by year, the second level might organize media files bymonth, and the third level might organize media files by event name. Inanother embodiment, the first level might organize media files by year,the second level might organize media files by month, the third levelmight organize media files by an event name, and the fourth level mightorganize media files by the media type.

Media file manager 332 could also organize media files into a linearslide structure such as slide structure 334, allowing a user to viewphotos and/or videos by sliding a view of a media file left or rightalong a user interface. Media file manager 332 could also organize mediafiles into a map view that shows a map, and allows a user to navigatethrough portions of the map in order to determine what media files weretaken in certain locations. The map view could also be organized in atree form, where the top level shows states, a middle level showscities, and a lowest level shows an intersection. Generally, where alocation is based upon a coordinate system, the levels of a map viewmight be delineated by a zoom level, where a zoom of 1 (the largest viewof the map) is a first level, a zoom of 2 is a second level, and so onuntil there exists only a single location—within that location being acollection of media files organized within an event name, and possiblymedia file type.

A user could send a request for a type of organization structure throughinterface module 310, and media file manager 332 could then provide aview of an organization structure, such as tree structure 332. The usercould then send a series of life album commands to navigate through thestructure, such as selecting the left branch, then the right branch, andthen a left branch, to reach a leaf of the tree, which represents amedia file. The user could then view the media file through a life albumuser interface. Preferably, the interface module 310 provides ways for auser viewing the media file to add additional user-generated metadatathat is associated with the media file. For example interface module 310provides an input comment field that accepts any of text content, audiocontent, and/or video content, or could provide a toggle that allows ause to mark that the media file is one of the user's “favorite” mediafile. A comment could be of any media content type, such as textcontent, audio content, or video content. As used herein, video contentcould be in the form of a series of images, or could be in the form of aseries of images with concurrent audio content. Such comments could besaved in memory and associated with the media file such that a user whoviews a media file can view the comments, whether the comments be text,audio, or video.

A user could also add a favorite toggle to a media file to mark themedia file as one of the user's favorite media files. The system wouldthen associate the media file with the user's account as a favoritemedia file, which could then be displayed by favorites module 222.

In FIG. 4, a software schematic 400 for a favorites module, such as myfavorites module 320, has a computer interface connection 410 and astorage interface 420. Interface connection 410 communicates with userinterface connections, such as through interface module 210, to providean opportunity for a user to review his/her own favorite media files.When interface connection 410 receives a request to view a user'sfavorite media files, the favorites module constructs a tree throughstorage interface 420. Storage interface 420 searches through its memoryto find media files that have been toggled as favorites of a user.Preferably, the memory holds a list of identifiers for each useraccount, where each identifier is a unique identifier for a media filesaved in storage, such as a pointer, to find the set of favoritestoggled media files. Storage interface could then construct a favoritesalbum tree structure as a function of the set of favorite toggled mediafiles. The tree structure could be at least two levels, three levels, orso on. In some embodiments, the storage interface could construct thefavorites album tree structure as a function of both the user-generatedmetadata and the computer-generated metadata. For example, at the firstlevel, the storage interface could divide the media files into mediafiles for a first child profile and a second child profile, and at thesecond level the storage interface could divide the media files intoevent names. In some embodiments the storage interface could merelyplace the favorite items into large buckets, where each bucket is achild profile. Preferably, the storage interface has a tree structurewhere the first level provides an identifier of the child profile thatthe media files belong to, the second level provides an identifier of atime period, such as a month, the third level provides an identifier ofan event name, and the fourth level provides an identifier of the mediafile. Any comments made by users are preferably displayed along with themedia file to the user interface.

In FIG. 5, a software schematic 500 for a model module, such as modelmodule 330, has a computer interface connection 510, a storage interface520, and a transaction interface 530. Interface connection 620 couldpresent a modeling user interface, preferably via an interface modulesuch as interface module 210, that allows a user to select one or moremedia files through storage interface 520. The user interface couldallow the user to select the media file through any sort of browsingstructure, such as the tree, slide, or map views of the life album userinterface, or the my favorites view of the favorites user interface.Once the user selected the media file, the user could also select amodeling agency from a list of modeling agencies provided to the userinterface by the model module. The media file 541 would likely be sentwith some metadata 542 that is associated with the media file, such as aunique identifier of the media file, an identifier of the child profileassociated with the media file, an identifier of the user sending themedia file, an identifier of one or more parents or guardians associatedwith the child profile, and/or a type of licensing contract. Once themedia file has been sent to the modeling agencys computer system viacomputer interface connection 510, the modeling agency could peruse themedia file and determine whether or not it wishes to license the mediafile.

If the modeling agency decides to license the file, the modeling agencycould then transmit a request for a license to computer interfaceconnection 510 with an offer of a contract 550. This contract could besent to the parent or guardian of the child by using an identifier inmetadata 542. The parent or guardian could then digitally sign contract550, and transaction module 530 would then transmit funds, credits, orother units of value from an account associated with the modeling agencyto an account associated with the parent or guardian, and would transfera digital license to the modeling agency through interface connection510.

In FIG. 6, a software schematic 600 for a competition module, such ascompetition module 340, has a computer interface connection 620, and astorage interface 640. Computer interface connection 620 generallycommunicates with a plurality of different user interfaces 611, 612,613, and 614, possibly through an interface module such as interfacemodule 210. A user of the interface module could send a command throughthe provided competition user interface to send a selected media file asan entry to a competition. Preferably, the system is configured suchthat each user account is allowed to submit only one media file at atime. Such functionality could be achieved, for example, by setting upthe system such that when a user tries to submit a second media file toa competition, the system either refuses to submit the second mediafile, or supplants the first submitted media file with the second mediafile. The system could provide a competition user interface to a userthat allows the user to peruse through media files that the user hasaccess to, such as through a life album browsing structure or myfavorites browsing structure, and select a media file to submit as acompetition entry.

Software schematic 600 shows various media files 631, 633, 635, and 637which have been selected by different users as entries to a competition.These media files are compiled and shown to various user interfaces,such as user interfaces 611, 612, 613, and 614 via computer interfaceconnection 620 to allow the user interfaces to vote on a media file.Preferably, the system is set up such that each user account is onlyallowed to vote once for a competition. At the end of a competition(i.e. when a month has passed for a monthly competition, or when a yearhas passed for a yearly competition), the system could tally the numberof votes for each of the media files entered into the competition, andprovide an indicator to at least one of the competition user interfacesregarding which media file is the winner of the competition. Theindicator is generally calculated as a function of each of the tally ofvotes.

In FIG. 7, a software schematic 700 for a face transformation module,such as face transformation module 350, has a computer interfaceconnection 710, a media file storage interface 720, and a video storageinterface 730. The computer interface connection 710 generally isconfigured to present a face transformation user interface to a user viacomputer interface connection 710. Through the face transformation userinterface, a user could select a series of photos in a life album fromwhich a face transformation video could be constructed. In a preferredembodiment, the system will automate this process by selecting the mostrelevant photos available to construct a face transformation video.

In some embodiments, a user will send a command through the facetransformation user interface that the user wishes to construct a facetransformation video from a child's life album. This is generallyperformed by a parental user who selects a button such as “generate facetransformation video” and then selects one of the parental user'schildren. Since each child is generally associated with a different lifealbum, the system could then peruse through the life album for validmedia files that could be used to generate a face transformation video.

The system generally has a default algorithm that could be used togenerate a face transformation video. For example, a default algorithmcould be a system that automatically selects the most appropriate imagefrom every month, every week, or every day in a life album to constructa face transformation video. In some embodiments, the system could beconfigured to display, via the face transformation user interface, someof the default settings and allow a user to change a setting. Forexample, the face transformation user interface could reveal to the userthat default settings automatically select the most appropriate photofrom every week of available photos in a life album, and construct avideo based upon those most appropriate photos. A user could then alterthe default settings to automatically select a photo within every 30 daytime period, every 15 day time period, every 10 day time period, every 5day time period, every 3 day time period, or every day. Where as timeperiod (such as a month, week, or day) in the life album does not haveany photos, the system could skip that photo.

The system could be configured to select the most appropriate photowithin a time period of the life album using a variety of differenttechniques. For example, the system could derive a facial clarify valuefor each of the images in a time period (including images within a videomedia file), and select the image having the highest facial clarityvalue for a face that matches an identifying image for the life album.Images that fail to have a face that matches the identifying image forthe life album are generally not considered as candidate images by theface transformation module. As used herein, a “facial clarity value” isa metric measured from 0 to 100 that reflects how much of a face isshown in an image. For example, an image showing only the back of aperson's head would have a facial clarity value of 0, an image showingthe profile of a person might have a facial clarity value of 20, and animage showing a plan view of a person's face might have a facial clarityvalue of 100. A simple facial clarity algorithm might identify a numberof identifying features in the life profile's identifying image, divide100 by that number to get a value x, and then add x to the facialclarity value for every identifying feature found in an image. A morerobust facial clarity algorithm might weight the facial clarity value byfeature importance. For example an identifying nose, mouth, and eyesmight have twice as much weight as an identifying cheek, mole, and earsfor a face. In a preferred embodiment, the system would automaticallyselect an image having the highest facial clarity value within a timeperiod. Where a plurality of images have the highest facial clarityvalue within the time period, the system preferably selects the mostrecent image taken.

In some embodiments, the user might alter the defaults such that theuser is able to select the images used in the face transformation video.Preferably, for each time period, the system provides the user with alist of images having a derived facial clarity value above a predefinedthreshold facial clarity value, such as 70 or 80. The system could rankeach of the presented images, such that the images having the highestfacial clarity value are presented higher in the list before the imageshaving a lower facial clarity value. The user could then select an imagefrom each presented set of images for each time period, selecting aplurality of images to be used for the resultant face transformationvideo.

Once the images are selected (either automatically or through manualselection by the user), the system preferably aligns each of the imageswith one another as a function of the facial features detected in eachimage. For example, the system could detect a centerline of each face,and orient all of the images such that the centerlines of each face ineach image aligns with a centerline of the video. Or the system coulddetect an area of each image that has a nose, and align the images suchthat each nose location overlaps the location of the next and/orprevious images nose location. Or the system could detect an angle ofthe face in each image, and ensure that all of the angles of the face inall of the images match one another. In a preferred embodiment, thesystem could provide an interface to the face transformation userinterface allowing a user to manipulate an angle and a size of the facein the first image of the face transformation video, and the systemcould then ensure that all of the later faces in the face transformationvideo are aligned with the manipulated first image.

In some embodiments, the system could zoom in or zoom out on a face toensure that the face in each image is within a threshold volume. Forexample, the system could set the face transformation video to ensurethat an area of a face in each image is within 70-80% of the total areaof an image. Where an image is used having a face below the thresholdpercentage gap, the system could zoom in on the face until the face hasan area at least the area of the lowermost threshold percentage. Wherean image is used having a face above the threshold percentage gap, thesystem could zoom out on the face until the face has an area at most thearea of the higher threshold percentage. Contemplated threshold sizesalso include exact thresholds, for example a threshold ensuring that thearea of every face in a face transformation video has an area of 75% ofthe total size of the image.

The selected and aligned images are then combined by the module into avideo 750. Here, the selected images are 741, 743, and 745 withassociated metadata 742, 744, and 746, respectively. The metadataassociated with each image comprises, for example, a timestampassociated with the image, a facial clarity, whether the image wasselected for use in a face transformation video, and how the image hasbeen rotated, zoomed, and/or cropped in order to be aligned with theother images in the video. The video is then stored into the memory viavideo storage module 730, which generally saves the video in a separatepart of memory than the life album storage. Video storage module 730also saves each selected image and metadata associated with each image.In the future when a user wishes to construct a new, updated facetransformation video, the system could automatically select thepreviously selected images by default. In this manner, a user who hasalready selected images for use in a previous video does not need tore-select images from previously reviewed time periods, and only newtime periods that have not been reviewed yet could be examined

In FIG. 8, a software schematic 800 for a parental collaboration module,such as parental collaboration module 360, has a computer interfaceconnection 810, a comment storage interface 830, and an expert interfaceconnection 840. Computer interface connection 810 communicates with aplurality of parental collaboration user interfaces such as userinterface 811, user interface 812, user interface 813, and userinterface 814, possibly via interface module 210. Each user interface811 812, 813, and 814 is preferably functionally coupled to computerinterface connection 810 using a different parental user account. When auser of a parental user account submits a comment 851, metadata 852about the parental user account and what comment thread the commentshould be associated with is also saved. Here, the different userinterfaces submit comment 851 having metadata 852, comment 853 havingmetadata. 854, comment 855 having metadata 856, and comment 857 havingmetadata 858.

Computer interface connection 810 generally provides a parentalcollaboration user interface to each of user interfaces 811, 812, 813,and 814. A user from any user interface could send a comment generationrequest to the user interface, requesting the system to generate acomment thread. In some embodiments, comment threads are associated witha media file, such as any of the media files in a child's life album.When a user views the media file by navigating to the leaf of a lifealbum, the user could also have access to contribute one or morecomments to the child life albums comment thread. In such embodiments,the system preferably allows only a parent or guardian of the child'slife album to generate a comment thread for the media file, and allowsparents or guardians of a child's life album to set privacy permissions,allowing a subset of users to view a media file, and/or a subset ofusers to contribute to the comment thread associated with the mediafile. The system could be configured to automatically create a commentthread with every media file in a life album by default, allowing aparent of a child's life album to alter the defaults through aconfiguration user interface. For example, a parent could reset thesystem to automatically create comment threads for media files of aselected event, but not to automatically create comment threads formedia files of unselected events.

A user could also send a request for the parental collaboration userinterface to create a comment thread associated with a comment threadtitle topic, such as, “What is the best way for me to home school anautistic child?” Users could peruse a parental collaboration forum forsuch titles, and contribute comments to that comment thread. In someembodiments, the user who creates such a comment thread, could also setpermissions allowing a selected subset of users to contribute commentsto the comment thread. The system could allow users to define such asubset dynamically, for example a group of users who are defined by anadmin user such as a. homeschool group whose admin user controls whichhomeschool parents are allowed to be defined as a member of thehomeschool group. Users within that group creating a comment threadthrough the parental collaboration user interface could then define thecomment thread to only be accessed by members of the group. The systemwould generally hide a comment thread from users who do not have accessto the comment thread, or could show the title of the comment thread,but not the contents of the comment thread to users who have not beengiven access by an admin user.

Once a comment thread has been created, users who have access to thecomment thread are generally allowed to contribute comments, such ascomments 851, 853, 855, and 857. Such comments are saved into a commentthread by comment storage interface 830. Comments could be in the formof text, audio, or video submissions. In order for the computer systemto parse though audio or video submissions, the system preferably uses avoice recognition software to convert the content into parsable text,such as those disclosed in U.S. 2015/0012.260 to Chakladar. U.S. Pat.No. 8,812,325 to Burns, U.S. Pat. No. 8,671,149 to Baxter, or U.S. Pat.No. 8,660,847 to Soemo, each of which is incorporated herein byreference.

Once two or more comments have been generated, the system preferablyautomatically derives one or more common issues for the comment thread.Common issues for the comment thread could be determined, for example,by detecting a recurring unquoted phrase among the comments. Sincesingle words like “the” “and” and “or” tend to be commonly used among aplurality of different comments, the system preferably onlyautomatically detects recurring unquoted phrases of a certain minimumlength, such as three words, four words, five words, or more. Theminimum length is typically predefined by an admin user of the system.As discussed previously, an “unquoted phrase” is a new phrase that hasbeen generated by the comment submitter, as opposed to a phrase that wasincluded as a quote by the confluent submitter. Users that submitcomments could be given the option to include a quote from a previouscomment in order to give the new comment context. Such quotes arepreferably excluded from analysis by the system.

In some embodiments, the system could be configured to only look forphrases that have been defined by an admin user through the parentalcollaboration user interface, such as “autistic child” or “AMID.” Theparental collaboration user interface could also be configured to allowan admin user to define literal phrase equivalents, for example an adminuser could draw an equivalent between the phrase, “ADHD,” “AttentionDeficit Disorder,” and “Attention Deficit Hyperactivity Disorder.” Insome embodiments, a phrase might be an entire sentence and include aperiod, for example, “My child has nightmares.” or “I wish I could sleepbetter at night.” In some embodiments, a user could highlight a phrasein a comment field and submit it as an identified phrase that is apotential common issue. The system could then review the comment threadfor recurrences of that identified phrase (and any literal equivalentsdefined by the system) to find how often that issue might have recurredin the comment thread.

The system could then review the list of detected common issues, andautomatically select the common issue having the highest recurrence, andgenerate a comment thread summary as a function of the common issue. Insome embodiments, an admin user might select the common issue to besummarized from a list of common issues presented to the admin user.Such a list could be filtered to only show the top common issues, or toonly show common issues having a minimum recurrence (e.g. a minimumrecurrence of 25, 50, 75, 100, or 150).

In a simple embodiment, such a summary could consist of only a list ofthe common issues with hyperlinks to the comment containing the commonissue. In a preferred embodiment, the summary could consist of all ofthe literal equivalents along with a quantity next to each equivalentlisting how many times that literal equivalent has been used. Suchsummaries preferably include hyperlinks to the comment to allow a userreviewing the summary to delve into the summary to find specificinstances of the recurring issue to review.

Once a summary has been created, the system could then be configured toexport the comment thread summary 851 of the most prominent common issueto an expert interface connection 840. Expert interface connection 840transmits the comment thread summary to a remote expert computer system,which processes the comment thread summary and returns an answer 852 tobe incorporated into the comment thread summary. An example of apreferred expert interface connection is an email that is automaticallysent to the email address of a psychology expert who reviews thesummary, generates as response that is emailed back to the expertinterface connection 840 and the response 852 is then saved into thecomment thread by comment storage interface 830.

In some embodiments comment thread summary is only generated and sentafter a request for an expert answer has been requested by a user whohas access to the comment thread. In other embodiments, a comment threadsummary is only generated and sent after a threshold number of usershave requested an expert answer through the parental collaboration userinterface. For example, an admin could configure the system to onlydetect, summarize, and send a common issue to an expert when at least 10users have sent a request for an expert answer through the parentalcollaboration user interface.

It should be apparent to those skilled in the art that many moremodifications besides those already described are possible withoutdeparting from the inventive concepts herein. The inventive subjectmatter, therefore, is not to be restricted except in the scope of theappended claims. Moreover, in interpreting both the specification andthe claims, all terms should be interpreted in the broadest possiblemanner consistent with the context. In particular, the terms “comprises”and “comprising” should be interpreted as referring to elements,components, or steps in a non-exclusive manner, indicating that thereferenced elements, components, or steps may be present, or utilized,or combined with other elements, components, or steps that are notexpressly referenced. Where the specification claims refers to at leastone of something selected from the group consisting of A, B, C . . . andN, the text should be interpreted as requiring only one element from thegroup, not A plus N, or B plus N. etc.

What is claimed is:
 1. A non-transitory computer-readable medium formanaging a plurality of child profiles, comprising instructions storedthereon, that when executed on a processor, perform the steps of:associating a plurality of media files with a first child profile of theplurality of child profiles; receiving a first favorite toggle commandfrom the media file view user interface to toggle a first media file ofthe plurality of media files as a favorite of the first plurality ofmedia files: receiving a second favorite toggle command from the mediafile view user interface to toggle a second media file of the pluralityof media files as a favorite of the first plurality of media files;generating a favorites album tree structure as a function of a set offavorite toggled media files of the first plurality of media files,wherein the favorites album tree structure has (a) at least two levels,(b) an identifier of the first child profile as a first node, (c) anidentifier of the toggled first media file as a first leaf of the firstnode (d) an identifier of the toggled second media file as a second leafof the first node, (e) the first input comment associated with the firstleaf, and (f) the second input comment associated with the second leaf:and providing the favorites album tree structure to a favorites userinterface.
 2. The non-transitory computer-readable medium of claim 1,wherein the first plurality of media files comprises timestamp metadata.3. The non-transitory computer-readable medium of claim 2, furthercomprising automatically assigning a first time category and a secondtime category to each of the first plurality of media files as afunction of the timestamp metadata.
 4. The non-transitorycomputer-readable medium of claim 3, further comprising generating afirst life album tree structure of the first plurality of media files asa function of the first time category and the second time category. 5.The non-transitory computer-readable medium of claim 4, wherein each ofthe first plurality of media files is represented by a different lifealbum leaf of the first life album tree structure.
 6. The nun-transitorycomputer-readable medium of claim 4, wherein, the first life album treestructure has at least three levels.
 7. The non-transitorycomputer-readable medium of claim 6, further comprising navigating afirst path in response to a first set of life album commands from thelife album user interface, wherein first path travels through the firstlife album tree structure to a first life album leaf of the first lifealbum tree structure, wherein the first life album leaf represents afirst media file of the first plurality of media files.
 8. Thenon-transitory computer-readable medium of claim 1, further comprisingproviding the first plurality of media files to the life album userinterface having a favorite toggle interface that allows a user totransmit the first favorite toggle command and the second favoritetoggle command.
 9. The non-transitory computer-readable medium of claim1, further comprising providing a first input comment field for a firstmedia file of the first plurality of media files to a media file viewuser interface, wherein the first input comment field is configured toreceive a video comment, an audio comment, and a text comment.
 10. Thenon-transitory computer-readable medium of claim 1, wherein theinstructions are further configured to perform the steps of: receiving arequest from a modeling user interface to send the first media file to adistal modeling computer system; transmitting the first media file tothe distal modeling computer system for review receiving a purchaseorder for a license to the first media file; debiting an account as afunction of the purchase order; and transmitting a license to a modelingentity as a function of the purchase order.
 11. The non-transitorycomputer-readable medium of claim 1, wherein the instructions arefurther configured to perform the steps of: receiving a command from acompetition user interface to send the first media file as an entry to acompetition; saving the first media file to a competition databasehaving a plurality of competition media files, including the first mediafile; providing the competition media files to a plurality of othercompetition user interfaces as entrants to the competition; receiving aplurality of votes for a portion of the plurality of competition mediafiles from the plurality of other competition user interfaces;calculating a tally of votes for each of the plurality of competitionmedia files; and providing an indicator of a winner of the competitionto the competition user interface, wherein the indicator is calculatedas a function of each of the tally of votes for each of the plurality ofcompetition media files.
 12. The non-transitory computer-readable mediumof claim 2, wherein the instructions are further configured to performthe steps of: receiving a command from a face transformation userinterface to generate a thee transformation video; selecting a firstfacial image from the first plurality of media files as a function ofthe timestamp metadata; selecting a second facial image from the firstplurality of media files as a function of the timestamp metadata;deriving a first set of facial features from the first facial image anda second set of facial features from the second facial image; generatingthe face transformation video containing the first facial image and thesecond facial image that aligns the second facial image with the firstfacial image as a function of the first set of facial features and thesecond set of facial features; saving the face transformation video to aface transformation memory location; and presenting the facetransformation video to the face transformation user interface.
 13. Thenon-transitory computer-readable medium of claim 12, wherein theinstructions are further configured to perform the steps of: generatinga comment thread in response to a comment generation request from aparental collaboration user interface; saving a first comment from afirst parent of the first child profile to the comment thread; saving asecond comment from a second parent of a second child profile to thecomment thread; automatically deriving a first common issue among aplurality of comments saved to the comment thread; generating a commentthread summary as a function of the first common issue; exporting thecomment thread summary to an expert user interface; receiving an expertanswer from the expert user interface; saving the expert answer to anexpert section of the comment thread, and presenting the expert answerto the parental collaboration user interface.
 14. The non-transitorycomputer-readable medium of claim 12, wherein the step of selecting thefirst facial image from the first plurality of media files as a functionof the timestamp metadata comprises: selecting a first subset of imagesfrom the first plurality of media files, wherein each of the firstsubset of images has a timestamp within a first time period; deriving afacial clarity value for each of the subset of images; and selecting thefirst facial image from the first subset of images as a function of itsderived facial clarity value.
 15. The non-transitory computer-readablemedium of claim 14, wherein the step of selecting the first subset ofimages from the first plurality of media files comprises separating avideo media file into a plurality of images for review.
 16. Thenon-transitory computer-readable medium of claim 15, wherein the step ofselecting the first subset of images from the first plurality of mediafiles comprises: identifying features of a child profile face in animage associated with the first child profile; and comparing theidentified features against the first plurality of media files.
 17. Thenon-transitory computer-readable medium of claim 14, wherein the step ofselecting the first facial image from the first subset of images as afunction of its derived facial clarity value comprises: selecting asecond subset of images from the first subset of images wherein each ofthe second subset of images has a derived facial clarity value above apredefined threshold facial clarity value; providing the second subsetof images to the face transformation user interface; and receiving aselection of the first facial image from the face transformation userinterface.
 18. The non-transitory computer-readable medium of claim 12,wherein the step of selecting the first facial image from the firstplurality of media files as a function of the timestamp data comprises:selecting a first subset of images from the first plurality of mediafiles, wherein each of the first subset of images has a timestamp withina first time period; providing the first subset of images to the facetransformation user interface; and receiving a selection of the firstfacial image from the face transformation user interface.
 19. Thenon-transitory computer-readable medium of claim 12, wherein theinstructions are further configured to perform the step of receiving afirst time period and a second time period from the face transformationuser interface, wherein the step of selecting the first facial imagefrom the first plurality of media files as a function of the timestampmetadata comprises selecting the first facial image from a first subsetof images having a timestamp within the first time period, and whereinthe step of selecting the second facial image from the second pluralityof media files as a function of the timestamp metadata comprisesselecting the second facial image from a second subset of images havinga timestamp within the second time period.
 20. The non-transitorycomputer-readable medium of claim 12, wherein the first set of facialfeatures comprise a first nose location, wherein the second set offacial features comprise a second nose location, and wherein aligningthe second facial image with the first facial image comprises aligningthe second nose location to overlap the first nose location.